-
Notifications
You must be signed in to change notification settings - Fork 14k
See if this is the time we can remove layout::size_align
#149109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
See if this is the time we can remove `layout::size_align`
This comment has been minimized.
This comment has been minimized.
This was a bad idea before, but now that `size_of` and `align_of` work completely differently than when removing it was first tried in 2020, maybe it makes sense now. (Or maybe I'll just add another attempt to the list in the comments...)
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (032b547): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 3.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.1%, secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 477.858s -> 472.077s (-1.21%) |
2bf4c01 to
30f4a2a
Compare
|
@rustbot ready Those perf results look clearly not-worse to me, and they might be amazing if that bootstrap saving 4.441 seconds on a single crate ( (It's probably not actually that good, but I'm happy to take less "weird enough to need a comment" code in the library for what looks like it's probably a small net perf improvement.) |
|
That's a world of difference from the 5-25% regressions in #72189 (cc @nnethercote in case that's been in the back of your head). Great work compiler team.
No idea why, don't think I've touched this code 😆 but it works for me @bors r+ |
|
Haha, nice! |
|
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 7281a3b (parent) -> 53732d5 (this PR) Test differencesShow 26 test diffs26 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 53732d5e076329a62f71d3c6901886ce8a71e812 --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (53732d5): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowOur benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 1.4%, secondary -1.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -2.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.1%, secondary -0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 472.196s -> 471.595s (-0.13%) |
|
Ok, those perf results make more sense. Still seem roughly neutral-to-green, which is all I was going for with a cleanup -- as tgross35 mentioned previous attempts were obviously worse than neutral. |
|
Negative results are all noise ( |
|
@rustbot label: +perf-regression-triaged |
This was a bad idea before, but now that
size_ofandalign_ofwork completely differently than when removing it was first tried in 2020, maybe it makes sense now.(Or maybe I'll just add another attempt to the list in the comments...)
r? ghost